Dynamic user equipment (UE) group creation to coordinate devices

ABSTRACT

A network function selectively supports a mobile device with network settings appropriate for the device context of the mobile device. The network function obtains a device profile for the mobile device, which identifies multiple device groups, with each device group being associated with a corresponding set of network settings. The network function selects a device group among the device groups in the device profile based on the device context of the mobile device. The network function directs at least one network function in the network to support the mobile device with a set of network settings corresponding to the selected device group.

TECHNICAL FIELD

The present disclosure relates to wireless network systems andsupporting groups of mobile devices.

BACKGROUND

User Equipment (UE) group creation is a popular concept where variousUEs are grouped together and provisioned in Fifth Generation (5G)Network Functions (NFs) for a common policy and user experiences. As perthe current architecture, the grouping of UEs is done statically at thetime of provisioning of UEs in 5G NFs, e.g., Unified Data Management(UDM) or Home Subscriber Server (HSS).

The Third Generation Partnership Project (3GPP) has defined a UEInternal-Group identifier, but this group identifier is static innature. Once a UE is configured for a particular group, the UE cannotleave that group unless the network re-provisions the UE. The UEInternal-Group identifier does not include dynamic group formation withdynamic policies attached to the device groups.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified block diagram of a network system, according toan example embodiment.

FIG. 2 is a message flow diagram illustrating messages within a networksystem to provision the network system to support a mobile device,according to an example embodiment.

FIG. 3 is a message flow diagram illustrating messages within a networksystem to update the device profile of a mobile device, according to anexample embodiment.

FIG. 4A is a message flow diagram illustrating messages within a networksystem to update the device context of a mobile device, according to anexample embodiment.

FIG. 4B is a message flow diagram illustrating messages within a networksystem to update the network settings of a mobile devices based on theirdevice context, according to an example embodiment.

FIG. 5 is a flowchart illustrating operations performed at a PolicyControl Function (PCF) in a network system to support a mobile devicebased on a device context, according to an example embodiment.

FIG. 6 illustrates a simplified block diagram of a device that may beconfigured to perform the methods presented herein, according to anexample embodiment.

DESCRIPTION OF EXAMPLE EMBODIMENTS

Overview

A computer implemented method is provided for a network function toselectively support a mobile device with network settings appropriatefor the device context of the mobile device. The method includesobtaining a device profile for the mobile device, which identifies aplurality of device groups, with each device group being associated witha corresponding set of network settings. The method also includesselecting a first device group among the plurality of device groupsbased on the first device context of the mobile device. The methodfurther includes directing at least one network function in the networkto support the mobile device with a first set of network settingscorresponding to the first device group.

Example Embodiments

The emergence of new use cases for wireless network systems generates ademand for dynamic creation of User Equipment (UE) groups based onQuality of Service (QoS) needs. Dynamic creation of UE groups may allowFifth Generation (5G) Network Functions (NFs) to add and remove mobiledevices from various QoS groups supported by the NFs. The mobile devicesmay join or leave different QoS groups based on factors (e.g., physicallocation, application usage, time of day, operator policy, etc.) thatchange more often than a 5G network re-provisions the mobile device.Changing the device policy allows the mobile device to leave or to joinany device group at any time without changing the configuration of themobile device.

The Policy Control Function (PCF) of the 5G network uses the ApplicationFunction (AF) influence to determine which device group is the mostappropriate for each mobile device based on the device context.Additionally, different network functions (e.g., User Plane Functions)may be selected based on the device group to allow better coordinationand more predictable response time (e.g., lower latency) for trafficbetween mobile devices in the same device group.

The techniques presented herein enable a network function to group UEsinto device groups based on the services each mobile device isrequesting. A UE may belong to multiple device groups, but the networkmay select network settings (e.g., a QoS group) based on variousfactors, such as the services the UE is requesting, physical location ofthe UE, and/or time of day. The network may also select the same 5G NFs(e.g., Session Management Function (SMF) or UPF) based on the devicegroup to provide the UE a better quality of experience.

In one example use case, healthcare appliances may be grouped accordingto their use in different healthcare settings (e.g., remote assistedsurgery/operation). In a hospital setting, various types of instrumentsand devices are available for surgeries. Depending on current surgicalneeds, some of the devices/instruments may be moved between operatingtheaters, which may be specific to different types of surgery. For eachparticular surgery, the supporting network coordinates all of thedevices/instruments for that particular surgery by grouping thedevices/instruments and providing the same network setting (e.g., QoSgroup) based on the device group. The specific device group may dependupon the type of surgery and the physical location of the operatingtheater.

For instance, in a first operation in a first operating theater, threedevices (e.g., heart monitor, blood monitor, and fluoroscope) may berequired for the first operation. The network may group these threedevices in a common device group while they are being used within thefirst operating theater. When a second operation in a second operatingtheater requires devices (e.g., heart monitor, blood monitor, endoscope)that may or may not be the same devices from the first operation, thenetwork may group these devices in a different device group withdifferent network settings. When any device (e.g., heart monitor orblood monitor) moves back and forth between operating theaters, thenetwork switches the device group for that device and supports thedevice with the appropriate network settings (e.g., QoS group, NFselection) for the operating theater.

In another example use case, participants in online conferences may moveinto different conference rooms or other physical locations.Additionally, dedicated devices for online conferences (e.g.,telepresence endpoints) may be associated with a particular physicalconference room that may be used for different online conferences. Thenetwork may support a particular online conference by grouping all ofthe endpoint devices (e.g., group endpoints, single user endpoints,smart phones, etc.) that are participating in the particular onlineconference into a single device group to coordinate the traffic for theparticular online conference. A mobile device may be switched to adevice group dedicated to the particular online conference based on themobile device joining the particular online conference, or based on themobile device entering a physical conference room scheduled for theparticular online conference. Once the device context of the mobiledevice places the mobile device in the appropriate device group for theparticular online conference, the network supports the mobile device, aswell as the other devices participating in the particular onlineconference, with network settings that coordinate and optimize thetraffic for the particular online conference.

Referring now to FIG. 1 , an example of a network system 100 configuredto support a UE 110 (e.g., a mobile device) with dynamic device groupsis shown. The UE 110 connects to the network through a Radio AccessNetwork (RAN) 115, which may include a next generation Node B (gNB). Thenetwork system 100 also includes an Access Management Function (AMF) 120that is configured to handle connection and mobility management tasksfor the network system 100.

The network system 100 also includes an SMF 130 that is configured tomanage data sessions and the session context for UEs, such as UE 110,that are attached to the network system 100. The network system 100includes UPF 140 and UPF 145, which are configured to manageinterconnecting with one or more data networks 150, as well as managethe packet handling and QoS requirements for Protocol Data Unit (PDU)sessions with the UE 110.

The network system 100 further includes a PCF 160 configured to providepolicy rules for control plane functions (e.g., network slicing,roaming, etc.) in the network system 100. The PCF 160 is also configuredto support QoS policy and charging functions and manage networkresources based on operator policies. The PCF 160 includes device grouplogic 165 that enables the PCF 160 to dynamically group mobile devices(e.g., UE 110) into device groups appropriate for the context of eachmobile device.

The network system 100 includes a Unified Data Repository (UDR) 170 thatis configured to provide data storage services to the network system100. The UDR 170 includes records with subscriber data, device data, anddata related to network services. The UDR 170 stores the device grouppolicy 175, which provides the PCF 160 with the device group informationto make a determination on which device group the UE 110 belongs. Insome instances, a Unified Data Management (UDM) element (not shown) mayalso be included in network system 100 to facilitate various datastorage/retrieval services.

The network system 100 also includes a Network Exposure Function (NEF)180 that is configured to provide a secure point to interface withoutside entities, such as an Application Function (AF) 185. In oneexample, the AF 185 may be an online conferencing server or a schedulingsystem for operating theaters in a healthcare setting.

In one example, a network operator may define device groups to includeQoS groups, each identified by a group identifier, e.g., an alphanumericvalue. Each QoS groups may be associated with a different QoS profile,depending on the use case for the device group. A mobile device, such asUE 110, may be provisioned (e.g., in the UDR 170) to be part of one ormore QoS groups initially. Subscription data for a mobile device mayassociate the subscriber with particular QoS groups.

In another example, multiple mobile devices (e.g., UE 110) in the sameuse case (e.g., participating in an online conference) may be assignedto the same device group. The PCF 160 may ensure that all of the mobiledevices in a device group are assigned to the same SMF (e.g., SMF 130)and the same UPF (e.g., UPF 140) for better latency between the membersof the device group. Grouping the mobile devices with the same SMF andUPF enables a Multi-Access Edge Computing (MEC) use case for dynamicallydefined device groups.

The group identifiers corresponding to a mobile device (e.g., UE 110)may be provided to the PCF 160 by the UDR 170. The PCF 160 may use thegroup identifier to select an SMF (e.g., SMF 130) and push a QoS profilematching the QoS group of the mobile device. The SMF 130 may use the QoSprofile and/or the group identifier to select an appropriate UPF (e.g.,UPF 140 or UPF 145) and apply the QoS profile rules to the selected UPF.Additionally, the SMF 130 and/or the PCF 160 may use QoS groupinformation for differentiated charging rules based on device group usecases.

Referring now to FIG. 2 , an example of a message flow 200 in thenetwork system 100 to add a device profile for a mobile device (e.g., UE110) is shown. FIG. 2 includes UPF 140, SMF 130, PCF 160, UDR 170, NEF180, and AF 185. Various operations for FIG. 2 are discussed withreference to a mobile device, such as UE 110, however, a mobile deviceis not shown in FIG. 2 for purposes of brevity only in order toillustrate other features of the network system 100. The AF 185initiates the message flow by sending a request 210 to the NEF 180. Inone example, the request 210 is a Traffic Influence (TI) request thatidentifies the mobile device and the new device profile.

In one example, the TI sent at 210 may be formatted as any of anNnef_TrafficInfluence_Create/Update/Delete message/operation, as definedby 3GPP standards. The device profile may include one or more devicegroups that may be appropriate for the mobile device depending on thedevice context of the mobile device. For instance, the device profilemay include a first device group that is appropriate for a first devicecontext (e.g., general interne traffic) and a second device group for asecond device context (e.g., participating in an online conference). Adevice group may be associated with a QoS group (e.g., specific QoSnetwork settings). However, a device group may be associated with othernetwork settings which may not be specifically designed to affect QoSfor network traffic.

The NEF 180 receives the request 210 from the AF 185 and forwards thenew device profile 215 to the UDR 170. In one example, the NEF 180 mayadjust the format of the new device profile based on requirements and/orpreferences of the NEF 180. In another example, the new device profilemay include a wildcard entry to enable the new device to join any devicegroup that may be defined in the UDR 170. The NEF 180 sends a response220 to the AF 185 to confirm that the new device profile has beenreceived and forwarded to the UDR 170.

The UDR 170 stores the new device profile 215 and notifies the PCF 160of the device profile with a notification 230. In one example, thenotification 230 may be formatted as a Nudr_DataManagement(DM)_Notifyoperation/message, e.g., as described in the 3GPP TechnicalSpecification 23.502. The PCF 160 makes a policy decision on whichdevice group to place the mobile device and sends a session management(SM) policy request 240 to the SMF 130 to support the mobile device withnetwork settings appropriate for the selected device group. In oneexample, the policy request sent at 240 may be formatted as anNpcf_SM_PolicyControl_Update_Notify_Request message/operation, asdefined by 3GPP standards. The SMF 130 acknowledges the sessionmanagement policy request 240 by sending a session management policyresponse 245 to the PCF 160, and coordinates in an exchange 250 with theUPF 140 to configure or reconfigure the user plane for the mobiledevice. In one example, the response sent at 245 may be formatted as anNpcf_SM_PolicyControl_Update_Notify_Response message/operation, asdefined by 3GPP standards.

The AF 185 may initiate a similar message flow to update or delete adevice profile from the UDR 170 by sending another TI request to the NEF180. The AF 185 would identify the mobile device and device profile toupdate/remove in the new TI request, and the other NFs (e.g., NEF 180,UDR 170, PCF 160, SMF 130, and UPF 140) reconfigure the support of themobile device accordingly, without reconfiguring the mobile deviceitself.

Although a mobile device, such as UE 110, may be provided with a devicegroup and corresponding network settings (e.g., QoS settings) in theinitial provisioning, the PCF 160 may change the device group andcorresponding network settings for the UE 110 based on the devicecontext for the UE 110 (e.g., the service requested by the UE 110, thephysical location of the UE 110, the time of day, etc.). When a mobiledevice, such as UE 110, starts or stops a particular applicationtraffic, the AF 185 may use traffic routing procedures (e.g., asdescribed in 3GPP technical specification 23.501) to notify the NEF 180of the change in application traffic. The NEF 180 may interact with theUDR 170 to update the device profile for the mobile device andcreate/update/delete one or more device groups for the device profile ofthe mobile device.

Referring now to FIG. 3 , an example of a message flow 300 in thenetwork system supporting a healthcare scheduling system is shownupdating a device profile for a mobile device. FIG. 3 includes UPF 140,SMF 130, PCF 160, UDR 170, NEF 180, and AF 185. Various operations forFIG. 3 are discussed with reference to various mobile devices, no mobiledevices are shown in FIG. 3 for purposes of brevity only in order toillustrate other features of the network system 100. The UDR 170includes device profiles 310 for two mobile devices (e.g., device A anddevice B). The device profile for device A includes two devicegroups—Group 1 that is appropriate when device A is used in operatingtheater 1 (e.g., for a liver operation), and Group 2 that is appropriatewhen device A is used in operating theater 2 (e.g., for an operation ona patient's lungs). Similarly, the device profile for device B includestwo device groups—Group 1 that is appropriate when device B is used inoperating theater 1 (e.g., for a liver operation), and Group 3 that isappropriate when device B is used in operating theater 2 (e.g., for aheart operation).

In one example, the specific data network (e.g., otl-liver.com) may beone of the parameters defined by the device group. For instance, all ofthe devices in a device group may use the same data network tofacilitate coordinated usage/latency of data between the devicesassigned to the device group. However, a specific data network is notnecessarily exclusive to a specific device group. Additionally, a devicegroup may include multiple data networks in certain use cases. In otherwords, many use cases associate a device group with a specific datanetwork, but some use cases may not associate the data network as aspecific parameter of the device group.

The AF 185 sends a request 320 to modify the device profile for one ofthe devices (e.g., Device A) to the NEF 180. The NEF 180 forwards thedevice profile 322 to the UDR 170, and sends a response 324 to the AF185 acknowledging the device profile modification request. In oneexample, the request 320 and response 324 may be formatted as an NEF_TIexchange. The UDR 170 stores the updated profile at 330 (e.g., addingGroup 3 to Device A that is appropriate when Device A is used inoperating theater 2 for a heart operation), and sends a notification 340to the PCF 160 of the updated device profile.

The PCF 160 stores the updated device profile and makes a policydecision on the device group based on the updated device profile at 345.In one example, the PCF 160 may determine that the device A should beswitched from Group 2 to Group 3, for instance because the device A isbeing used in operating theater 2 for a heart operation instead of for aliver operation. The PCF 160 sends a policy update request 350 to theSMF 130, which confirms the policy update with a policy update response355. Based on the policy decision 345, the SMF 130 and the UPF 140reconfigure the user plane 360 for the device A. For instance, the SMF130 may cause the UPF 140 to connect to a different data network that isassociated with heart operations in operating theater 2, instead of adata network associated with liver operations in operating theater 2.

In one example, the PCF 160 may determine an appropriate device groupfor the UE 110, and based on the device context (e.g., device location),the PCF 160 may push network settings (e.g., policy rules) for thedevice group to the SMF 130 along with a QoS profile for the devicegroup. The SMF 130 may apply the network settings (e.g., QoS rules) forthe PDU session of the UE 110 and reconfigure the UPF 140 to use thenetwork settings, if needed. Additionally, the SMF 130 may choose thesame UPF 140 for all of the UEs belonging to the same device group,based on network operator policy, and configure the same QoS rules toensure a consistent quality of experience.

Referring now to FIG. 4A and FIG. 4B, an example of a message flow 400in the network system supporting an online conferencing application isshown updating a device context for a mobile device. FIGS. 4A and 4Binclude UE 110, gNB 115, AMF 120, SMF 130, UPF 140, UPF 145, PCF 160,UDR 170, NEF 180, and AF 185. Various operations for FIGS. 4A and 4B arediscussed with reference to a UE 110 or other mobile devices, however,messages between the mobile devices (e.g., UE 110) and the gNB 115 arenot explicitly shown in FIGS. 4A and 4B. The UE 110 is combined with thegNB 115 in FIGS. 4A and 4B for purposes of brevity only in order toillustrate other features of the network system 100.

The UDR 170 includes device profiles 405 for two mobile devices (e.g.,device A and device B). The device profile for device A includes twodevice groups—Group 1 that is appropriate for general internet data, andGroup 2 that is dedicated to an online conference. In one example, Group2 may be specific to a particular online conference. Alternatively,Group 2 may be appropriate for all online conferences joined by deviceA. Similarly, the device profile for device B includes two devicegroups—Group 2 that is dedicated to an online conference, and Group 3that is appropriate when device B is used in a particular location(e.g., a San Jose corporate campus).

In this example, the gNB 115 registers the UE 110 with the networkthrough the AMF 120 in an exchange 410, and the AMF 120 sends anotification 412 to the UDR 170 about the UE 110 registering with thenetwork. The UE 110 establishes a PDU session in an exchange 414 withthe SMF 130. The SMF 130 establishes an N4 connection 416 with the UPF140 to support the PDU session with the UE 110. In one example, the PCF160 may provide network settings to the SMF 130 and/or the UPF 140 thatdetermine QoS settings for the PDU session for the UE 110 based on thedevice group (e.g., Group 1) selected for the UE 110. The UPF 140 and/orthe SMF 130 notifies the UDR 170 about the registration and subscriptioninformation of the UE 110 in an exchange 418. Once the SMF 130 and theUPF 140 apply the Group 1 settings at 420, the UE 110 may commence adata session 425 through the UPF 140.

The AF 185 detects a change in the device context of the UE 110 (e.g.,the UE 110 joined an online conference) and sends an update message 430to the NEF 180. The update message 430 identifies the device context(e.g., a request to join the online conference, entering a physicalconference room associated with the online conference, a predeterminedtime associated with the online conference, etc.) and may identify theUE 110. In one example, update message 430 may identify PDU session ofone or more UEs (e.g., UE 110). In another example, the update sent at430 may be formatted as any of an Nnef_TrafficInfluence_Create/Updatemessage/operation, that includes an AF service identifier for the AF 185and a traffic type identifier identifying the traffic for which theupdate is to be applied. For instance, the traffic type identifier maybe represented by a combination of Data Network Name (DNN),Single-Network Slice Selection Assistance Information (S-NSSAI), and/orapplication identifiers/traffic filtering information, such as a 5-tupleof source IP address, source port number, destination IP address,destination port number, and protocol. The AF service identifier mayrefer to an application handling user plane traffic for the UE 110 andmay be used by the UPF (e.g., UPF 140 or UPF 145) to detect trafficassociated with the application.

The NEF 180 passes the device context update 432 to the UDR 170, whichstores the new device context at 434. The NEF sends a device contextnotification 436 to the PCF 160, which updates the policy decision at440. In one example, the PCF 160 determines that Group 2 is moreappropriate for the UE 110 than Group 1, based on the new devicecontext.

As shown in FIG. 4B, the updated policy decision 440 causes the PCF 160to send a policy update request 450 to the SMF 130, which responds witha policy update response 452. Based on the updated device group (e.g.,Group 2) indicated by the policy update request 450, the SMF 130 makes aUPF decision 454, which determines that the UE 110 will join the onlineconference through UPF 145, i.e., a different UPF than the originallynegotiated connection as shown in FIG. 4A. The SMF 130 reconfigures theuser plane for the UE 110 in an exchange 460, switching the PDU sessionfor the UE 110 to a different UPF 145. This enables the UE 110 toseamlessly proceed with a data session 465 using the network settings(e.g., QoS settings) associated with Group 2. The network adjusts thenetwork settings associated with UE 110 to address the change in devicecontext without changing the configuration of the UE 110 orre-provisioning the UE 110.

When a new device (e.g., device B) joins the same online conference asthe UE 110, the AF 185 sends another notification 470 to the NEF 180 toensure that the devices in the same online conference are placed in thesame device group and supported by the same network settings. The NEF180 forwards the notification 472 to the UDR 170, which notifies the PCF160 with a notification 474. The PCF 160 makes a policy decision 480 toplace the new device in the same device group (e.g., Group 2).

The PCF 160 sends a policy update request 482 to the SMF 130, whichacknowledges the new device in the device group by sending a policyupdate response 484 to the PCF 160. The SMF 130 reconfigures the userplane for the new device in an exchange 490 to use the same UPF 145 thatthe UE 110 is using for the online conference. The new device (e.g.,device B) is assigned to the same device group (e.g., group 2) with thesame network settings as network uses to support the original UE 110(e.g., device A) in the online conference, and begins to communicate inthe online conference through data session 495. In one example, any orall of the devices participating in a particular online conference maybe assigned to the same device group to ensure a consistent quality ofexperience for the online conference.

Referring now to FIG. 5 , a flowchart illustrates operations performedby a network function (e.g., PCF 160) in a process 500 to support amobile device (e.g., UE 110) with a device profile including multipledevice groups. At 510, the network function obtains a device profile fora mobile device. The device profile identifies multiple device groupsassociated with corresponding set of network settings. In one example,the network settings may include QoS groups. At 520, the networkfunction selects a first device group from the device profile based on afirst device context of the mobile device. In one example, the firstdevice context may include the location of the mobile device, the timeof day, and/or specific application traffic requested by the mobiledevice.

At 530, the network function directs at least one other network functionto support the mobile device with a first set of network settingscorresponding to the first device group. In one example, the PCF (e.g.,PCF 160) may direct an SMF (e.g., SMF 130) to support the mobile devicewith specific QoS settings. Additionally, the PCF may direct the SMF toselect a particular UPF (e.g., UPF 140 or UPF 145) corresponding to thefirst device group.

Until the network function detects a new device context for the mobiledevice at 540, then the network function continues to support the mobiledevice with the first set of network settings corresponding to the firstdevice group. If the network function detects a second device contextfor the mobile device at 540, then the network function directs the atleast one other network function support the mobile device with a secondset of network settings corresponding to a second device group at 550.In one example, the PCF network function may be notified from the UDR(e.g., UDR 170) that an AF (e.g., AF 185) has updated the devicecontext.

Referring to FIG. 6 , FIG. 6 illustrates a hardware block diagram of acomputing device 600 that may perform functions associated withoperations discussed herein in connection with the techniques depictedin FIGS. 1-3, 4A, 4B, and 5 . In various embodiments, a computingdevice, such as computing device 600 or any combination of computingdevices 600, may be configured as any entity/entities as discussed forthe techniques depicted in connection with FIGS. 1-3, 4A, 4B, and 5 inorder to perform operations of the various techniques discussed herein.

In at least one embodiment, the computing device 600 may include one ormore processor(s) 602, one or more memory element(s) 604, storage 606, abus 608, one or more network processor unit(s) 610 interconnected withone or more network input/output (I/O) interface(s) 612, one or more I/Ointerface(s) 614, and control logic 620. In various embodiments,instructions associated with logic for computing device 600 can overlapin any manner and are not limited to the specific allocation ofinstructions and/or operations described herein.

In at least one embodiment, processor(s) 602 is/are at least onehardware processor configured to execute various tasks, operationsand/or functions for computing device 600 as described herein accordingto software and/or instructions configured for computing device 600.Processor(s) 602 (e.g., a hardware processor) can execute any type ofinstructions associated with data to achieve the operations detailedherein. In one example, processor(s) 602 can transform an element or anarticle (e.g., data, information) from one state or thing to anotherstate or thing. Any of potential processing elements, microprocessors,digital signal processor, baseband signal processor, modem, PHY,controllers, systems, managers, logic, and/or machines described hereincan be construed as being encompassed within the broad term ‘processor’.

In at least one embodiment, memory element(s) 604 and/or storage 606is/are configured to store data, information, software, and/orinstructions associated with computing device 600, and/or logicconfigured for memory element(s) 604 and/or storage 606. For example,any logic described herein (e.g., control logic 620) can, in variousembodiments, be stored for computing device 600 using any combination ofmemory element(s) 604 and/or storage 606. Note that in some embodiments,storage 606 can be consolidated with memory element(s) 604 (or viceversa), or can overlap/exist in any other suitable manner.

In at least one embodiment, bus 608 can be configured as an interfacethat enables one or more elements of computing device 600 to communicatein order to exchange information and/or data. Bus 608 can be implementedwith any architecture designed for passing control, data and/orinformation between processors, memory elements/storage, peripheraldevices, and/or any other hardware and/or software components that maybe configured for computing device 600. In at least one embodiment, bus608 may be implemented as a fast kernel-hosted interconnect, potentiallyusing shared memory between processes (e.g., logic), which can enableefficient communication paths between the processes.

In various embodiments, network processor unit(s) 610 may enablecommunication between computing device 600 and other systems, entities,etc., via network I/O interface(s) 612 to facilitate operationsdiscussed for various embodiments described herein. In variousembodiments, network processor unit(s) 610 can be configured as acombination of hardware and/or software, such as one or more Ethernetdriver(s) and/or controller(s) or interface cards, Fibre Channel (e.g.,optical) driver(s) and/or controller(s), and/or other similar networkinterface driver(s) and/or controller(s) now known or hereafterdeveloped to enable communications between computing device 600 andother systems, entities, etc. to facilitate operations for variousembodiments described herein. In various embodiments, network I/Ointerface(s) 612 can be configured as one or more Ethernet port(s),Fibre Channel ports, and/or any other I/O port(s) now known or hereafterdeveloped. Thus, the network processor unit(s) 610 and/or network I/Ointerface(s) 612 may include suitable interfaces for receiving,transmitting, and/or otherwise communicating data and/or information ina network environment.

I/O interface(s) 614 allow for input and output of data and/orinformation with other entities that may be connected to computingdevice 600. For example, I/O interface(s) 614 may provide a connectionto external devices such as a keyboard, keypad, a touch screen, and/orany other suitable input and/or output device now known or hereafterdeveloped. In some instances, external devices can also include portablecomputer readable (non-transitory) storage media such as databasesystems, thumb drives, portable optical or magnetic disks, and memorycards. In still some instances, external devices can be a mechanism todisplay data to a user, such as, for example, a computer monitor, adisplay screen, or the like.

In various embodiments, control logic 620 can include instructions that,when executed, cause processor(s) 602 to perform operations, which caninclude, but not be limited to, providing overall control operations ofcomputing device; interacting with other entities, systems, etc.described herein; maintaining and/or interacting with stored data,information, parameters, etc. (e.g., memory element(s), storage, datastructures, databases, tables, etc.); combinations thereof; and/or thelike to facilitate various operations for embodiments described herein.

The programs described herein (e.g., control logic 620) may beidentified based upon application(s) for which they are implemented in aspecific embodiment. However, it should be appreciated that anyparticular program nomenclature herein is used merely for convenience;thus, embodiments herein should not be limited to use(s) solelydescribed in any specific application(s) identified and/or implied bysuch nomenclature.

In various embodiments, entities as described herein may storedata/information in any suitable volatile and/or non-volatile memoryitem (e.g., magnetic hard disk drive, solid state hard drive,semiconductor storage device, random access memory (RAM), read onlymemory (ROM), erasable programmable read only memory (EPROM),application specific integrated circuit (ASIC), etc.), software, logic(fixed logic, hardware logic, programmable logic, analog logic, digitallogic), hardware, and/or in any other suitable component, device,element, and/or object as may be appropriate. Any of the memory itemsdiscussed herein should be construed as being encompassed within thebroad term ‘memory element’. Data/information being tracked and/or sentto one or more entities as discussed herein could be provided in anydatabase, table, register, list, cache, storage, and/or storagestructure: all of which can be referenced at any suitable timeframe. Anysuch storage options may also be included within the broad term ‘memoryelement’ as used herein.

Note that in certain example implementations, operations as set forthherein may be implemented by logic encoded in one or more tangible mediathat is capable of storing instructions and/or digital information andmay be inclusive of non-transitory tangible media and/or non-transitorycomputer readable storage media (e.g., embedded logic provided in: anASIC, digital signal processing (DSP) instructions, software[potentially inclusive of object code and source code], etc.) forexecution by one or more processor(s), and/or other similar machine,etc. Generally, memory element(s) 604 and/or storage 606 can store data,software, code, instructions (e.g., processor instructions), logic,parameters, combinations thereof, and/or the like used for operationsdescribed herein. This includes memory element(s) 604 and/or storage 606being able to store data, software, code, instructions (e.g., processorinstructions), logic, parameters, combinations thereof, or the like thatare executed to carry out operations in accordance with teachings of thepresent disclosure.

In some instances, software of the present embodiments may be availablevia a non-transitory computer useable medium (e.g., magnetic or opticalmediums, magneto-optic mediums, CD-ROM, DVD, memory devices, etc.) of astationary or portable program product apparatus, downloadable file(s),file wrapper(s), object(s), package(s), container(s), and/or the like.In some instances, non-transitory computer readable storage media mayalso be removable. For example, a removable hard drive may be used formemory/storage in some implementations. Other examples may includeoptical and magnetic disks, thumb drives, and smart cards that can beinserted and/or otherwise connected to a computing device for transferonto another computer readable storage medium.

Variations and Implementations

Embodiments described herein may include one or more networks, which canrepresent a series of points and/or network elements of interconnectedcommunication paths for receiving and/or transmitting messages (e.g.,packets of information) that propagate through the one or more networks.These network elements offer communicative interfaces that facilitatecommunications between the network elements. A network can include anynumber of hardware and/or software elements coupled to (and incommunication with) each other through a communication medium. Suchnetworks can include, but are not limited to, any local area network(LAN), virtual LAN (VLAN), wide area network (WAN) (e.g., the Internet),software defined WAN (SD-WAN), wireless local area (WLA) access network,wireless wide area (WWA) access network, metropolitan area network(MAN), Intranet, Extranet, virtual private network (VPN), Low PowerNetwork (LPN), Low Power Wide Area Network (LPWAN), Machine to Machine(M2M) network, Internet of Things (IoT) network, Ethernetnetwork/switching system, any other appropriate architecture and/orsystem that facilitates communications in a network environment, and/orany suitable combination thereof.

Networks through which communications propagate can use any suitabletechnologies for communications including wireless communications (e.g.,4G/5G/nG, IEEE 802.11 (e.g., Wi-Fi®/Wi-Fi6®), IEEE 802.16 (e.g.,Worldwide Interoperability for Microwave Access (WiMAX)),Radio-Frequency Identification (RFID), Near Field Communication (NFC),Bluetooth™ mm.wave, Ultra-Wideband (UWB), etc.), and/or wiredcommunications (e.g., T1 lines, T3 lines, digital subscriber lines(DSL), Ethernet, Fibre Channel, etc.). Generally, any suitable means ofcommunications may be used such as electric, sound, light, infrared,and/or radio to facilitate communications through one or more networksin accordance with embodiments herein. Communications, interactions,operations, etc. as discussed for various embodiments described hereinmay be performed among entities that may directly or indirectlyconnected utilizing any algorithms, communication protocols, interfaces,etc. (proprietary and/or non-proprietary) that allow for the exchange ofdata and/or information.

In various example implementations, entities for various embodimentsdescribed herein can encompass network elements (which can includevirtualized network elements, functions, etc.) such as, for example,network appliances, forwarders, routers, servers, switches, gateways,bridges, load balancers, firewalls, processors, modules, radioreceivers/transmitters, or any other suitable device, component,element, or object operable to exchange information that facilitates orotherwise helps to facilitate various operations in a networkenvironment as described for various embodiments herein. Note that withthe examples provided herein, interaction may be described in terms ofone, two, three, or four entities. However, this has been done forpurposes of clarity, simplicity and example only. The examples providedshould not limit the scope or inhibit the broad teachings of systems,networks, etc. described herein as potentially applied to a myriad ofother architectures.

Communications in a network environment can be referred to herein as‘messages’, ‘messaging’, ‘signaling’, ‘data’, ‘content’, ‘objects’,‘requests’, ‘queries’, ‘responses’, ‘replies’, etc. which may beinclusive of packets. As referred to herein and in the claims, the term‘packet’ may be used in a generic sense to include packets, frames,segments, datagrams, and/or any other generic units that may be used totransmit communications in a network environment. Generally, a packet isa formatted unit of data that can contain control or routing information(e.g., source and destination address, source and destination port,etc.) and data, which is also sometimes referred to as a ‘payload’,‘data payload’, and variations thereof. In some embodiments, control orrouting information, management information, or the like can be includedin packet fields, such as within header(s) and/or trailer(s) of packets.Internet Protocol (IP) addresses discussed herein and in the claims caninclude any IP version 4 (IPv4) and/or IP version 6 (IPv6) addresses.

To the extent that embodiments presented herein relate to the storage ofdata, the embodiments may employ any number of any conventional or otherdatabases, data stores or storage structures (e.g., files, databases,data structures, data or other repositories, etc.) to store information.

Note that in this Specification, references to various features (e.g.,elements, structures, nodes, modules, components, engines, logic, steps,operations, functions, characteristics, etc.) included in ‘oneembodiment’, ‘example embodiment’, ‘an embodiment’, ‘anotherembodiment’, ‘certain embodiments’, ‘some embodiments’, ‘variousembodiments’, ‘other embodiments’, ‘alternative embodiment’, and thelike are intended to mean that any such features are included in one ormore embodiments of the present disclosure, but may or may notnecessarily be combined in the same embodiments. Note also that amodule, engine, client, controller, function, logic or the like as usedherein in this Specification, can be inclusive of an executable filecomprising instructions that can be understood and processed on aserver, computer, processor, machine, compute node, combinationsthereof, or the like and may further include library modules loadedduring execution, object files, system files, hardware logic, softwarelogic, or any other executable modules.

It is also noted that the operations and steps described with referenceto the preceding figures illustrate only some of the possible scenariosthat may be executed by one or more entities discussed herein. Some ofthese operations may be deleted or removed where appropriate, or thesesteps may be modified or changed considerably without departing from thescope of the presented concepts. In addition, the timing and sequence ofthese operations may be altered considerably and still achieve theresults taught in this disclosure. The preceding operational flows havebeen offered for purposes of example and discussion. Substantialflexibility is provided by the embodiments in that any suitablearrangements, chronologies, configurations, and timing mechanisms may beprovided without departing from the teachings of the discussed concepts.

As used herein, unless expressly stated to the contrary, use of thephrase ‘at least one of’, ‘one or more of’, ‘and/or’, variationsthereof, or the like are open-ended expressions that are bothconjunctive and disjunctive in operation for any and all possiblecombination of the associated listed items. For example, each of theexpressions ‘at least one of X, Y and Z’, ‘at least one of X, Y or Z’,‘one or more of X, Y and Z’, ‘one or more of X, Y or Z’ and ‘X, Y and/orZ’ can mean any of the following: 1) X, but not Y and not Z; 2) Y, butnot X and not Z; 3) Z, but not X and not Y; 4) X and Y, but not Z; 5) Xand Z, but not Y; 6) Y and Z, but not X; or 7) X, Y, and Z.

Additionally, unless expressly stated to the contrary, the terms‘first’, ‘second’, ‘third’, etc., are intended to distinguish theparticular nouns they modify (e.g., element, condition, node, module,activity, operation, etc.). Unless expressly stated to the contrary, theuse of these terms is not intended to indicate any type of order, rank,importance, temporal sequence, or hierarchy of the modified noun. Forexample, ‘first X’ and ‘second X’ are intended to designate two ‘X’elements that are not necessarily limited by any order, rank,importance, temporal sequence, or hierarchy of the two elements. Furtheras referred to herein, ‘at least one of’ and ‘one or more of’ can berepresented using the ‘(s)’ nomenclature (e.g., one or more element(s)).

In summary, the techniques presented herein provide for UE groupingbased on QoS needs to better serve the use case for a group of UEs(e.g., Internet of Things (IoT) appliances, hospital instruments, onlineconference endpoints, etc.). A UE may be part of multiple device groupsinitially, but based on the service request (e.g., the PDU sessionrequest), the network may determine the appropriate device group andnetwork settings to suit the current traffic needs. The network pushescorresponding network settings (e.g., a QoS profile) to support the UEin the current device context of the UE. Additionally, other UEs in thesame device group may be supported with the same network settings, andmay be attached to the same NF instances to minimize the overall latencyand provide a better quality of experience for a data session betweenUEs of the same device group.

The device groups described herein are dynamic in nature. The AF mayinfluence the selection of the appropriate device group for each mobiledevice. The determination to select a particular device group for amobile device may be based on location or any other logic supported bythe AF. The device group may also be used by the SMF to ensure that allof the UEs in a particular device group use the same UPF instance.Additionally, the SMF/PCF may use the device group information fordifferentiated charging rules based on device group use cases.

In one form a method is provided for a network function to selectivelysupport a mobile device with network settings appropriate for a firstdevice context. The method includes obtaining a device profile for themobile device. The device profile identifies a plurality of devicegroups, with each device group being associated with a corresponding setof network settings. The method also includes selecting a first devicegroup among the plurality of device groups based on the first devicecontext of the mobile device. The method further includes directing atleast one network function in the network to support the mobile devicewith a first set of network settings corresponding to the first devicegroup.

In another form, an apparatus comprising a network interface and aprocessor is provided. The network interface is configured tocommunicate with a plurality of computing devices in a wireless networksystem. The processor is coupled to the network interface, andconfigured to obtain a device profile for a mobile device. The deviceprofile identifies a plurality of device groups, with each device groupbeing associated with a corresponding set of network settings. Theprocessor is also configured to select a first device group among theplurality of device groups based on a first device context of the mobiledevice. The processor is further configured to direct at least onenetwork function in a network to support the mobile device with a firstset of network settings corresponding to the first device group.

In still another form, a non-transitory computer readable storage mediais provided that is encoded with instructions that, when executed by aprocessor of network node of a network system, cause the processor toobtain a device profile for a mobile device. The device profileidentifies a plurality of device groups, with each device group beingassociated with a corresponding set of network settings. Theinstructions also cause the processor to select a first device groupamong the plurality of device groups based on a first device context ofthe mobile device. The instructions further cause the processor todirect at least one network function in a network to support the mobiledevice with a first set of network settings corresponding to the firstdevice group.

One or more advantages described herein are not meant to suggest thatany one of the embodiments described herein necessarily provides all ofthe described advantages or that all the embodiments of the presentdisclosure necessarily provide any one of the described advantages.Numerous other changes, substitutions, variations, alterations, and/ormodifications may be ascertained to one skilled in the art and it isintended that the present disclosure encompass all such changes,substitutions, variations, alterations, and/or modifications as fallingwithin the scope of the appended claims. For instance, the specific IEsdescribed are used as examples of IEs that are currently defined in 3GPPspecifications, but the techniques described herein may be adapted toother IEs that may be defined in current or future networkspecifications.

What is claimed is:
 1. A method comprising: obtaining a device profilefor a mobile device, the device profile identifying a plurality ofdevice groups, wherein each device group is associated with acorresponding set of network settings; selecting a first device groupamong the plurality of device groups based on a first device context ofthe mobile device; and directing at least one network function in anetwork to support the mobile device with a first set of networksettings corresponding to the first device group, wherein the at leastone network function is selected based on the first device group.
 2. Themethod of claim 1, further comprising: obtaining a notification of themobile device in a second device context; and responsive to thenotification, directing the at least one network function to support themobile device with a second set of network settings corresponding to asecond device group among the plurality of device groups.
 3. The methodof claim 2, further comprising: obtaining one or more additionalnotifications that one or more additional mobile devices are in thesecond device context; and supporting the one or more additional mobiledevices with the second set of network settings corresponding to thesecond device group.
 4. The method of claim 2, wherein the first devicecontext comprises a first physical location and the second devicecontext comprises a second physical location.
 5. The method of claim 2,wherein the second device context comprises participating in an onlineconference.
 6. The method of claim 2, wherein obtaining the notificationof the mobile device in the second device context comprises obtainingthe notification from an application function through a network exposurefunction.
 7. The method of claim 2, wherein the second set of networksettings comprises an indication of a particular User Plane Function(UPF) to support a Protocol Data Unit (PDU) session for the mobiledevice.
 8. The method of claim 2, wherein the second set of networksettings comprises one or more Quality of Service (QoS) settings fordata traffic to the mobile device.
 9. An apparatus comprising: a networkinterface configured to communicate with a plurality of computingdevices in a wireless network system; and a processor coupled to thenetwork interface, the processor configured to: obtain via the networkinterface, a device profile for a mobile device, the device profileidentifying a plurality of device groups, wherein each device group isassociated with a corresponding set of network settings; select a firstdevice group among the plurality of device groups based on a firstdevice context of the mobile device; and direct at least one networkfunction in a network to support the mobile device with a first set ofnetwork settings corresponding to the first device group, wherein the atleast one network function is selected based on the first device group.10. The apparatus of claim 9, wherein the processor is furtherconfigured to: obtain via the network interface, a notification of themobile device in a second device context; and responsive to thenotification, direct the at least one network function to support themobile device with a second set of network settings corresponding to asecond device group among the plurality of device groups.
 11. Theapparatus of claim 10, wherein the processor is further configured to:obtain via the network interface, one or more additional notificationsthat one or more additional mobile devices are in the second devicecontext; and support the one or more additional mobile devices with thesecond set of network settings corresponding to the second device group.12. The apparatus of claim 10, wherein the first device contextcomprises a first physical location and the second device contextcomprises a second physical location.
 13. The apparatus of claim 10,wherein the second device context comprises participating in an onlineconference.
 14. The apparatus of claim 10, wherein the second set ofnetwork settings comprises an indication of a particular User PlaneFunction (UPF) to support a Protocol Data Unit (PDU) session for themobile device.
 15. The apparatus of claim 10, wherein the second set ofnetwork settings comprises one or more Quality of Service (QoS) settingsfor data traffic to the mobile device.
 16. One or more non-transitorycomputer readable storage media encoded with software comprisingcomputer executable instructions and, when the software is executed on aprocessor of a network node of a network system, operable to cause aprocessor to: obtain a device profile for a mobile device, the deviceprofile identifying a plurality of device groups, wherein each devicegroup is associated with a corresponding set of network settings; selecta first device group among the plurality of device groups based on afirst device context of the mobile device; and direct at least onenetwork function in a network to support the mobile device with a firstset of network settings corresponding to the first device group, whereinthe at least one network function is selected based on the first devicegroup.
 17. The one or more non-transitory computer readable storagemedia of claim 16, wherein the software is further operable to cause theprocessor to: obtain a notification of the mobile device in a seconddevice context; and responsive to the notification, direct the at leastone network function to support the mobile device with a second set ofnetwork settings corresponding to a second device group among theplurality of device groups.
 18. The one or more non-transitory computerreadable storage media of claim 17, wherein the software is furtheroperable to cause the processor to: obtain one or more additionalnotifications that one or more additional mobile devices are in thesecond device context; and support the one or more additional mobiledevices with the second set of network settings corresponding to thesecond device group.
 19. The one or more non-transitory computerreadable storage media of claim 17, wherein the second set of networksettings comprises an indication of a particular User Plane Function(UPF) to support a Protocol Data Unit (PDU) session for the mobiledevice.
 20. The one or more non-transitory computer readable storagemedia of claim 17, wherein the second set of network settings comprisesone or more Quality of Service (QoS) settings for data traffic to themobile device.